Execution monitoring
The Debugger provides several ways to examine the state of an application. The following sections detail:
Code path analysis
During procedure execution, the Debugger window displays the listing of the procedure at each breakpoint or stopping point in its execution. A pointer always indicates the next line to execute. At any stopping point, you can display the listing for any procedure file using File
Open. This provides a convenient way to set breakpoints for any procedure in your environment, whether or not it is called from the procedure you are running.
You can examine and navigate the procedure call stack using the 4GL stack trace pane. This allows you to examine the current code path back and forth through the active series of procedure calls and triggers starting from the current stopping point.
Transaction monitoring
You can determine the transaction state of your application using Debug Show Transaction. This tells you whether a transaction is active at the current stopping point.
Breakpoint analysis
You can display the current breakpoint settings using Edit Breakpoints. This lists the breakpoints currently set for all procedures during the session. The listing for each executing procedure also indicates each line where a breakpoint is set.
Dynamic object monitoring
You can monitor the creation and destruction of dynamic object instances in your application, using Diagnostics Monitor Dynamic Objects. This lets you track dynamic object instances your application has created and not yet destroyed. This can help you locate unused object instances that can result in memory leaks.